Repository navigation
docs: make counter-evidence first-class - #63
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a counter-evidence ledger standard for Open Problem Lab.
This is deliberately not a new validator yet. It is a governance/documentation PR that defines how failed replications, null results, external-validity limits, dataset flaws, field contradictions, and unresolved reviewer objections should be preserved instead of disappearing into closed issues.
Why this matters
The highest-risk failure mode for a verification protocol is not lack of impressive accepted claims. It is selection bias: accepted evidence accumulates while disconfirming evidence becomes hard to find.
The new document introduces:
Safety / scope
Docs-only. No schema, workflow, or canonical problem-pack content is changed.
Review focus
Please review whether this should become a required artifact for mature problem packs, or stay advisory until a pack has enough accepted claims to justify it.